You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem Summary: Meta Service responses contain both an exact actual_code and a
legacy-compatible code. When a client recognizes the actual_code, it should use
that exact value. When actual_code is unknown, the legacy code is safe only if
it is explicitly present and non-OK. The previous logic could fall back to an
unset or OK code and incorrectly treat an unknown Meta Service error as success.
This change makes BE and FE fail closed with UNDEFINED_ERR in that case, while
preserving compatible non-OK fallbacks. It also adds a message explaining the
MS_TOO_BUSY to KV_TXN_CONFLICT conversion for legacy clients.
Release note
None
Check List (For Author)
Test
Regression test
Unit Test
Manual test (add detailed scripts or steps below)
No need to test or manual test. Explain why:
This is a refactor/code format and no logic has been changed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary: Meta Service responses contain both an exact actual_code and a
legacy-compatible code. When a client recognizes the actual_code, it should use
that exact value. When actual_code is unknown, the legacy code is safe only if
it is explicitly present and non-OK. The previous logic could fall back to an
unset or OK code and incorrectly treat an unknown Meta Service error as success.
This change makes BE and FE fail closed with UNDEFINED_ERR in that case, while
preserving compatible non-OK fallbacks. It also adds a message explaining the
MS_TOO_BUSY to KV_TXN_CONFLICT conversion for legacy clients.
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)